-
Notifications
You must be signed in to change notification settings - Fork 41.9k
Document that use of non idiomatic format for '@Value' still apply for environment variables #49054
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Thanks for the PR, but the line above your change has already that exact comment:
|
|
@wilkinsona made me aware that I read the wrong line, sorry about that. |
|
@linkian209 we need you to sign-off your commit as the DCO check fails at the moment. Can you please do that? |
This patch makes a small change to the documentation for External Configuration regarding how @value behaves with camelCase variables and environment variables. Signed-off-by: Ian Drake <linkian209@gmail.com>
Sorry about that! Done. |
See gh-49054 Signed-off-by: Ian Drake <linkian209@gmail.com>
|
Thanks @linkian209. We had a similar note for the binding in general so I've updated that as well in a polish commit. |
This patch makes a small change to the documentation for External Configuration regarding how
@Valuebehaves with camelCase variables and environment variables.I created a demo application that illustrates that variables that are defined using camelCase and injected using
@Valuenot in the canonical form will pickup values from environment variables.